home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
remote
/
callchek.zip
/
CALLCHEK.DOC
next >
Wrap
Text File
|
1992-04-16
|
37KB
|
776 lines
CallChek v1.9cß
(c) 1992 All Rights Reserved
RiverBend SoftWare
A RemoteAccess // Frontdoor
Log File Analizer
CallChek v1.9cß
- INDEX -
Instructions for using CallChek ......................... 1
Batch file use .......................................... 1
Combined log files ...................................... 1
Creating the control file ............................... 2
Errors .................................................. 4
Explanation of Report ................................... A
FrontDoor Log file (optional) ........................... 2
Location of CALLCHEK.EXE ................................ 1
Log files created by CallChek ........................... 4
Number of items reported ................................ 1
Other Logs .............................................. 3
Problems ................................................ 3
Quick start ............................................. 3
Reports created by CallChek ............................. B
Warranty ................................................ 1
This document has a page break // form feed every 55 lines
────────────────────
All the names of other software mentioned in this document are the
property of their respective owners/authors. These names are used
for explanation purposes only.
CallChek v1.9cß -1-
CallChek v1.9cß is a utility to read your RemoteAccess, and optionally
your FrontDoor, activity log. It provides, at this time 90 different items
of information about the activity on your BBS. It creates a straight ASCII
text file and an ANSI file in the directory of your choice. CallChek can be
run from its own seperate directory or any directory you put it in. I run it
from my RemoteAccess directory (C:\RA) but you can run it from wherever you
want just as long as it's control file is in the same directory and you tell
it where to find itself in the control file (CALLCHEK.CTL).
Depending on what options you have selected to appear in your Front-
Door log, the number of pieces of information reported may be less than 90.
It's best if all options are turned on for the FD Log and the expanded
version of the RA Log is used. If you combine your RA/FD logs into one, then
use that name in CALLCHEK.CTL where you name the RA Log AND where you name
the FD Log. It works, but it's really designed to read two seperate logs.
Results will be inaccurate if both Compact and Expanded formats are used in
the same RA Log.
CallChek is shareware. It is not freeware. You may try CallChek
for a period of 30 days. If, after the 30 day period has expired, you
continue to use CallChek you are obligated to register it with the author.
The registration cost of CallChek is Five Dollars ($5.00) US. See Order
form attached to this document.
CallChek comes with no warranty either expressed or implied. Use
it at your own risk. If your computer, monitor, hard drive, etc. breaks
in half while running CallChek, then you own both halves.
Appendix A contains a list of the different pieces of information
CallChek provides to the RA/FD SysOp.
CallChek can be run from a batch file during your daily maintenance
routine or straight from the command line. Just type CALLCHEK and press
your <Enter> key. It takes about 8 seconds to do its stuff when it's read-
ing a normal size RemoteAccess and/or FrontDoor activity log. It does not
keep a running total of anything but rather reads the entire log file each
time you run it. If you delete your activity log(s) each night (as I do)
then you'll get the figures for the current day, otherwise it will give you
figures from the start to the end of these files each time you run it.
The first thing you MUST DO prior to running CallChek is create a
short control file. This file MUST be named CALLCHEK.CTL and can be created
with any text editor that you have handy (I use QEdit). If you know how to
use the COPY CON command then you can create it that way. If you're a brain
surgeon, rocket scientist or short order cook, you can use the world famous
EDLIN that comes with DOS, ehummm. Just make sure the order shown in the
examples (see next page) is followed exactly. CALLCHEK.CTL must reside in
the same directory as CALLCHEK.EXE
Appendix A lists the items reported by CallChek and Appendix B is
an actual sample of the report created here on RiverBend.
CallChek v1.9cß -2-
CallChek requires a small control file called CALLCHEK.CTL and it
MUST BE IN THE SAME DIRECTORY AS CALLCHEK.EXE (no exceptions). The format
for this control file is as follows:
[ Start each line at the extreme left margin ]
BBS Name (EXACTLY as you have it in RAConfig and FDSetup)
SysOp Name (EXACTLY as you have it in RAConfig and FDSetup)
Drive and Path where you have your RemoteAccess Log (e.g. C:\BBS\LOGS\)
Name of your RemoteAccess Log (RA.LOG or whatever)
Drive and Path where you have CALLCHEK.EXE (e.g. D:\BBS)
Drive and Path where you want both copies of the Report placed (E:\RA\TEXT)
Name of ASCII Report you want created (such as CALLCHEK.ASC, etc)
Name of ANSI Report you want created (such as CALLCHEK.ANS, etc)
Drive and Path where you have your FrontDoor activity log (e.g. C:\FD)
Name of your FrontDoor Log (FD.LOG or whatever you call it)
My CALLCHEK.CTL looks like this:
Left margin ====>│RiverBend ─────┐
│Jim Tanner │ This file can be no longer than
│C:\RA\ │ the ten (10) lines as shown here.
│RA.LOG │
│C:\RA │ See the next example if you do not run
│C:\RA\TEXT\ │ FrontDoor as your frontend/mailer.
│CALLCHEK.ASC │
*** NEW *** => │CALLCHEK.ANS │ <───This line is **NEW** with v1.2ß
│C:\FD\ │
│FD.LOG ─────┘ NO BLANK LINES
[ A trailing back-slash after the Pathnames is optional ]
If you want CallChek to read your RA Log only then your CALLCHEK.CTL should
follow this format:
Line 1 ┌─── Your BBS Name (EXACTLY like you have it in RAConfig)
Line 2 │ SysOp name (EXACTLY like you have it in RAConfig)
Line 3 │ Drive:\Path\ to RemoteAccess Log (Include drive letter)
Line 4 │ Name of RemoteAccess log
Line 5 │ Drive:\Path\ to CALLCHEK.EXE and CALLCHEK.CTL
Line 6 │ Drive:\Path\ where you want the report placed
Line 7 │ Name of the ASCII Report to be created (FileName.Ext)
Line 8 │ Name of the ANSI Report to be created (FileName.Ext)
Line 9 │ ; <────────┐
Line 10 └─── ; <────────┴─────── Must be the last 2 lines
The ";" CAN ONLY BE USED ON THE LAST TWO LINES. If the format of
CALLCHEK.CTL is different from these examples shown then CallChek won't
give you accurate results. Shucks, it might not even run at all...
CallChek v1.9cß -3-
CallChek does not know anything about any other logs (and neither
do I) such as Binkley, D'Bridge, InterMail, SuperBBS, QuickBBS, etc. so
don't expect it to work with any of these logs. If you try it and it does
work, then it's strictly an accident. I've never seen any of these other
logs mentioned but if you care to send me a copy of any or all of them,
I'll be glad to try and adapt CallChek so that it will read them too.
CallChek will now create it's report in two formats (ASCII and ANSI)
The colors are not configurable at this time for the ANSI Report. The
ability to configure the colors *_may_* come later. The present colors
are Yellow on Blue.
As it is now, the report has a "ClearScreen" placed at the very top
and the RemoteAccess "Wait for Carraige Return" placed at the very bottom.
This is in case you want to make it available to your Callers as an option
to view at a RemoteAccess menu using the type 5 "Display Text File" option.
The next release is scheduled for whenever I get around to it and
that's as close as I'm gonna predict at this time. If there's no response
at all then there won't be another release. I know there's several other
programs that do basically the same thing as CallChek but I wanted some
things that these other programs didn't provide.
This release is NOT free for the asking. It's not crippled in any
way and won't ever expire. While I won't ever beg for money, if you wish
to send $5.00 US to further the cause, I'll be humble and accept it (Hell,
I ain't a complete fool). If you do register CallChek, I'll send you the
next release either on diskette via SnailMail or Netmail to your FIDO
address. It'll even flash your name up on the screen while it's doing its
business (hot diggity dawg..) and remove the "UNREGISTERED" at the top.
Please feel free to give copies of CallChek to your friends and
also upload it to as many Bulletin Boards as you can.
For a quick start, and to see what CallChek does, just throw a
copy of CALLCHEK.EXE in your RemoteAccess directory, complete the control
file (CALLCHEK.CTL) as described earlier and type CALLCHEK and press your
<Enter/Return> key. Then use a text file viewer such as LIST and you
can quickly tell whether you like it or not.
If you have any problems/questions/suggestions/ideas/compliments
then call RiverBend at (501) 563-6829 or send me NetMail at 1:19/99
You may also correspond with me in the RA_UTIL EchoMail Conference found
on most all RemoteAccess Boards. If you think you have found a bug in
CallChek, please notify me at once via NetMail at 1:19/99
Callchek v1.9cß -4-
ERRORS
──────
CallChek knows about some errors that might occurr and checks for
them upon initial startup and while it's running. If it encounters an
error that it recognizes, it will "beep" at you and then flash a short
note/explanation about the error on the screen for 5 seconds. It will
also create, on the fly, a text file called CALLCHEK.ERR and give a short
description of the error there. It will also give a possible solution
so you can fix whatever is wrong and try running CallChek again.
The most probable cause of errors with CallChek can usually be
traced to an error in CALLCHEK.CTL, the control file that CallChek depends
on to run properly. If anything there is misspelled, or a path name is
wrong, then an error will occur.
*** NOTE *** For CallChek to run at all, the Log file that you
designate as the RemoteAccess Log MUST already exist. If you try to
run CallChek and the log(s) don't exist then it's gonna "beep" at you
and stop.
LOG FILES
─────────
CallChek creates a record of its activity in a file (located in
the same directory where CALLCHEK.EXE is located) named CALLCHEK.LOG
This file is a straight ASCII text file and can be printed or viewed with
a program like LIST.COM
In addition to creating CALLCHEK.LOG, CallChek will also append
a line to the RemoteAccess Log and FrontDoor Log showing the time it was
run.
If your logs are not real large, CallChek can be run after each
Caller quits and your batch file returns control to either RemoteAccess
or FrontDoor. CallChek usually takes about 8 - 10 seconds to run thru
two logs that contain about 25 calls (incoming and outgoing).
I run CallChek during my midnight maintenance and my main batch
file tells DOS to change to the directory where CALLCHEK.EXE and the
control file, CALLCHEK.CTL are located (e.g. CD \RA) then the next line
says CALLCHEK That's all there is to it. You can, optionally, tell
DOS to copy the last report created by CallChek to another directory (or
rename them is their present directory) before you run CallChek during
the midnight maintenance. This will give you a copy of the previous days
report to compare with the current day.
CallChek v1.9cß
--- Appendix A ---
-A/1-
EXPLANATION OF REPORT GENERATED
───────────────────────────────
TOTAL CALLS The number of calls (IN and OUT) the
─────────── system handled during the time period
of the current log files.
TOTAL CALLS RCVD The number of calls that came IN to your
──────────────── system during the time period of the log
files. This is the totals of the BBS
calls plus calls that was handled only
by the mailer (FrontDoor).
TOTAL CALLS OUT The number of OUTgoing calls that was
─────────────── placed by the mailer (FrontDoor). This
does not include any calls made by the
SysOp using the Terminal within Front-
Door.
MAIL CALLS RCVD The number of calls that came IN to your
─────────────── system and was handled by FrontDoor and
not passed on the RemoteAccess.
BBS CALLS RCVD The number of calls that was passed on to
────────────── RemoteAccess. These are human callers
going on to your BBS.
CONNECT SPEEDS This is a listing of CONNECT speeds which
────────────── was reported by FrontDoor. This list will
show the speeds for both INcoming calls
and OUTgoing calls combined. It does not
differentiate between the two at this time.
This list starts at 300 BPS and goes up to
16800 BPS.
CONNECT TYPES This is a list showing the different types
───────────── of connections reported by FrontDoor. If
a calls comes in and FrontDoor reads it as
being 9600/ARQ/HST/HST/V42BIS then each of
these types will be counted. (HST/HST/) is
only counted as one HST. IEMSI calls are
reported by RemoteAccess.
DOWNLOADS The number of DownLoads reported by Remote
───────── Access.
UPLOADS The number of UpLoads reported by Remote
─────── Access.
CallChek v1.9cß
-A/2-
FILES SENT The number of Files sent OUT by FrontDoor
──────────
FILES/PKTS RCVD The number of Files, Mail Packets, etc.
─────────────── received by FrontDoor.
FREQ RCVD The number of times your system received
───────── a File request from another remote system.
This figure represents the actual number
of individual File Requests received.
MAIL FILES RCVD The number of MAIL files received by your
─────────────── system. These files will all have a file
extension of ".MO1", ".TU1", ".WE2", etc.
indicating they contain one or more mail
packets (usually EchoMail).
INCOMPLETE PKTS This is the number of files that come IN
─────────────── to your system that are reported by Front
Door as being incomplete (usually an error
in the packet).
NODEDIFF/NODELIST RCVD The number of times FrontDoor receives a
────────────────────── file with a filename like NODELIST.A01 or
NODEDIFF.A07, etc.
ZIP - TIC FILES RCVD The number of files received through Fromt
──────────────────── Door that have one of these extensions.
READING MESSAGES The number of times your Callers in Remote
──────────────── Access select the Read Message option from
a menu. This is NOT the number of actual
messages read.
MESSAGES POSTED The number of Messages posted by Callers
─────────────── while online and in RemoteAccess.
MESSAGES DELETED The number of Messages that you or your
──────────────── Callers delete while online and in Remote
Access.
FILE ATTACH MESSAGES The number of Messages that Callers leave
──────────────────── while online in RemoteAccess that elect
to attach a file to the Message.
MSG BASE PACKED Reported when RAMSG packs the Message Base
───────────────
MSG BASE LINKED Reported when RAMSG links the Message Base
───────────────
CallChek v1.9cß
-A/3-
NETMAIL MSG RCVD The number of NetMail Messages that come
──────────────── IN to your system and are handled by Front
Door.
NULL MSG KILLED The number of null (empty) messages that
─────────────── are received by FrontDoor. These usually
come in as the result of a File Request.
PROTECTED SESSION The number of connections with a remote
───────────────── system (INcoming and OUTgoing) where the
two systems have an established Sessiom
Level PassWord setup between them.
LOCAL LOGON This is the number of times the SysOp or
─────────── CoSysOp logs onto RemoteAccess via the
KeyBoard. NOTE: This number is NOT in-
cluded in the Calls IN to the BBS.
NEWUSER CALLS The number of times a Caller completes the
───────────── New User procedure in RemoteAccess.
NO FULL NAME The number of times when a Caller does not
──────────── enter a full name when logging onto your
BBS. NOTE: If you allow one word names
this will not work.
NOT IN USER FILE When a call comes into RemoteAccess and
──────────────── the name entered is not found in the User
file. This can be a new Caller or one who
mispelled his/her name.
NORMAL LOGOFFS When a Caller uses the proper procedure to
────────────── end his/her call to RemoteAccess.
TIMELIMIT EXCEEDED When a Caller to RemoteAccess is cut off
────────────────── due to exceeding his/her time limit. This
can also occur when a Callers is cut off
due to an upcoming RemoteAccess Event.
INACTIVITY TIMEOUT When a Caller to RemoteAcces is cut off due
────────────────── not pressing a key within the time limit
you have specified in RAConfig.
LOST CARRIER When a call to RemoteAccess is ended due
──────────── the Caller "pulling the plug" or it can
also be due to other disruptions. At any
rate, the call was not terminated using
the proper logoff procedure.
CallChek v1.9cß
-A/4-
QUESTIONNAIRE The number of times a Questionnaire is
───────────── completed by a Caller to RemoteAccess. If
you have Questionnaires other than the
NewUser Questionnaire, then they will be
counted too.
DOS SHELLS Each time a Caller uses a menu type 7 or
────────── type 15 menu option in RemoteAccess. This
is usually "doors" to games, external Msg.
Editors, etc.
SYSOP PAGED The number of times your Callers attempted
─────────── to page the SysOp.
USER FILE SORTED Each time RAUSER sorts the User file.
────────────────
USER FILE PACKED Each time RAUSER packs the User file.
────────────────
USER REMOVED Each time RAUSER removes a name from the
──────────── User file.
SECLEVEL ALTERED This is reported each time a Caller's
──────────────── Security Level is altered as a result of
completing a Questionnaire in RemoteAccess.
INCORRECT PW The number of times your Callers enter an
──────────── incorrect PassWord when trying to enter
RemoteAccess.
EXCEEDED MAX PW The number of times your Callers exceed
─────────────── the maximum number of allowed attempts to
enter a correct PassWord. If you don't
have a limit set then this number won't be
reported.
MODEM FAILURE When RemoteAccess is unable to initialize
───────────── the modem.
MODEM FAILURE When FrontDoor is unable to initialize the
───────────── modem.
SHELL FROM KYBD When Alt-Z is pressed from KeyBoard
───────────────
REJECTED CALLS Reported by FrontDoor usually when a call
────────────── comes in and it's a human Caller wanting
to get into your Board during Zone Mail
Hour (or any time you don't allow Callers
access to your Board).
CallChek v1.9cß
-A/5-
PASSWORD ERRORS When FrontDoor connects to a remote system
─────────────── on INcoming and OUTgoing calls and an in-
correct PassWord is given to one system or
the other (occurs only on PassWord protect-
ed sessions in FrontDoor).
UNEXPECTED PW FrontDoor received a PassWord when it was
───────────── not expecting one. If you have a session
level PassWord establised with a remote
system and the remote uses an AKA that
you don't have setup, then this will get
reported as an Unexpected PassWord.
HANDSHAKE FAILURE When FrontDoor is unable to "shake hands"
───────────────── with a remote system (reported on both
INcoming and OUTgoing calls).
EMSI FAILURE When FrontDoor receives a call and the
──────────── remote is attempting an EMSI connection
and is unable to connect properly.
TIMEOUT RCVD When FrontDoor receives a "Timeout" on
──────────── either INcoming or OUTgoing calls.
UNABLE TO SEND FILE When FrontDoor is unable to send a file
─────────────────── to a remote system.
ERRORLEVEL EXITS When FrontDoor exits for an "X" Event as
──────────────── specified in the FrontDoor SetUp options.
These "X" Events are ErrorLevel Events
as defined in FDSetUp.
MAIL RCVD EXIT When FrontDoor exits after mail is received
──────────────
TRUNCATED FILE When FrontDoor truncates a sent file (this
────────────── is usually an EchoMail packet)
IGNORED FREQ FrontDoor ignored a FileRequest (usually
──────────── because the requesting system is not list-
ed in the current NodeList.
MAILER TYPES The different types of Mailers that your
──────────── system has a connection with. Not all
Mailers are listed here but this is all
that I've had connections with and was
able to see how it was reported in the
FrontDoor Log.
CallChek v1.9cß
--- Appendix B ---
Sample of Report generated by CallChek
──────────────────────────────────────
Registered to: RiverBend * * * Home of CallChek
RiverBend activity as of: 04-15-1992
╓───────────────────────────────────────────────────────────╖
║ ║
║ ═════ MAIN SYSTEM Activity ════════════════════════════ ║
║ ║
║ ╒════════════════════════════════════════════╕ ║
║ │ Total System Calls (Rcvd + Made) ... 27 │ ║
║ ╘════════════════════════════════════════════╛ ║
║ ║
║ Description: Nmbr Description: Nmbr ║
║ ───────────────────── ──── ──────────────────── ──── ║
║ Total Calls Rcvd .... 23 Total Calls Made.... 4 ║
║ Mail Calls Rcvd ..... 12 BBS Calls Rcvd ..... 11 ║
║ ║
║ CONNECT Speeds (INcoming and OUTgoing Calls) ║
║ ║
║ 300 Baud ............ 0 1200 Baud .......... 0 ║
║ 2400 Baud ........... 7 4800 Baud .......... 0 ║
║ 9600 Baud ........... 13 12000 Baud ......... 0 ║
║ 14400 Baud .......... 7 16800 Baud ......... 0 ║
║ ║
║ CONNECT Types (INcoming and OUTgoing Calls) ║
║ ║
║ HST ................. 6 ARQ ................ 6 ║
║ V42BIS .............. 11 V32Bis ............. 2 ║
║ V32 ................. 7 MNP ................ 3 ║
║ LAPM ................ 6 EMSI ............... 16 ║
║ IEMSI ............... 1 NonIEMSI ........... 3 ║
║ ║
║ ═════ FILE System ═════════════════════════════════════ ║
║ ║
║ RemoteAccess ═══════ ║
║ ║
║ DownLoads ........... 36 UpLoads ............ 7 ║
║ ║
║ FrontDoor ══════════ ║
║ ║
║ Files Sent .......... 16 Files/Pkts Rcvd .... 6 ║
║ FREQ Rcvd ........... 11 Mail Files Rcvd .... 2 ║
║ Incomplete Pkts ..... 0 NodeDiff Rcvd ...... 0 ║
║ NodeList Rcvd ....... 0 ZIP Files Rcvd ..... 2 ║
║ ARJ Files Rcvd ...... 3 LZH Files Rcvd ..... 1 ║
║ ARC Files Rcvd ...... 0 SDN Files Rcvd ..... 0 ║
║ SDS Files Rcvd ...... 0 PAK Files Rcvd ..... 0 ║
║ FLE Files Rcvd ...... 0 TIC Files Rcvd ..... 0 ║
║ BAD Files Rcvd ...... 0 ZOO Files Rcvd ..... 0 ║
║ ║
║ ═════ MESSAGE System ══════════════════════════════════ ║
║ ║
║ Description: Reported by: ║
║ ───────────────────── ──────────────────── ║
║ Reading Messages .... 7 RemoteAccess ............. ║
║ Messages Posted ..... 15 RemoteAccess ............. ║
║ Messages Deleted .... 12 RemoteAccess ............. ║
║ Msg Base Packed ..... 1 RemoteAccess ............. ║
║ Msg Base Linked ..... 1 RemoteAccess ............. ║
║ FileAttach Message .. 3 RemoteAccess ............. ║
║ NetMail Msg Rcvd .... 3 FrontDoor ................ ║
║ Null Msg Killed ..... 2 FrontDoor ................ ║
║ ║
║ ═════ MISC ════════════════════════════════════════════ ║
║ ║
║ Description: Reported by: ║
║ ───────────────────── ──────────────────── ║
║ Local LogOn ......... 1 RemoteAccess ............. ║
║ NewUser Calls ....... 2 RemoteAccess ............. ║
║ No Full Name ........ 1 RemoteAccess ............. ║
║ Not In User File .... 2 RemoteAccess ............. ║
║ Normal LogOffs ...... 8 RemoteAccess ............. ║
║ TimeLimit Exceeded .. 1 RemoteAccess ............. ║
║ Inactivity TimeOut .. 1 RemoteAccess ............. ║
║ Lost Carrier ........ 2 RemoteAccess ............. ║
║ Questionnaire ....... 2 RemoteAccess ............. ║
║ DOS Shells .......... 8 RemoteAccess ............. ║
║ SysOp Paged ......... 2 RemoteAccess ............. ║
║ User File Sorted .... 1 RemoteAccess ............. ║
║ User File Packed .... 1 RemoteAccess ............. ║
║ User Removed ........ 2 RemoteAccess ............. ║
║ SecLevel Altered .... 2 RemoteAccess ............. ║
║ Incorrect PW ........ 1 RemoteAccess ............. ║
║ Exceeded Max PW ..... 0 RemoteAccess ............. ║
║ Modem Failure ....... 0 RemoteAccess ............. ║
║ Modem Failure ....... 1 FrontDoor ................ ║
║ Shell From KyBd ..... 3 FrontDoor ................ ║
║ Protected Session ... 3 FrontDoor ................ ║
║ Rejected Calls ...... 0 FrontDoor ................ ║
║ PassWord Errors ..... 1 FrontDoor ................ ║
║ Unexpected PW ....... 0 FrontDoor ................ ║
║ HandShake Failure ... 1 FrontDoor ................ ║
║ EMSI Failure ........ 0 FrontDoor ................ ║
║ TimeOut Rcvd ........ 2 FrontDoor ................ ║
║ Unable To Send ...... 0 FrontDoor ................ ║
║ ErrorLevel Exits .... 2 FrontDoor ................ ║
║ Mail Rcvd Exit ...... 6 FrontDoor ................ ║
║ Truncated Sent File . 2 FrontDoor ................ ║
║ Ignored FREQ ........ 0 FrontDoor ................ ║
║ ║
║ ║
║ MAILER Types (INcoming and OUTgoing Calls) ............ ║
║ ║
║ FroDo Commercial .... 4 FrontDoor ................ ║
║ FroDo NC ............ 10 FrontDoor ................ ║
║ BinkleyTerm ......... 0 FrontDoor ................ ║
║ InterMail ........... 1 FrontDoor ................ ║
║ TIMS ................ 0 FrontDoor ................ ║
║ D'Bridge ............ 1 FrontDoor ................ ║
║ Dutchie ............. 0 FrontDoor ................ ║
╙───────────────────────────────────────────────────────────╜
CallChek v1.9cß
CallChek v1.9cß Registration Form
Date:______________
Name .......... __________________________________________________
Exactly as shown in RA Config and FD SetUp
BBS Name ...... __________________________________________________
Exactly as shown in RA Config and FD SetUp
BBS Phone ..... (_____) - _____ - ____________
FIDO Address .. __________________________________________________
Show Zone:Net/Node/Point
BOSS Node ..... __________________________________________________
Use this ONLY if you are a Point system
Your Name ..... __________________________________________________
Mail Address .. __________________________________________________
City/ST/Zip ... __________________________________________________
Type of payment: [ ] Money Order [ ] Personal Check [ ] Cash
──────────────────────────────
Your registered copy of CallChek will be sent to your FIDO address
via NetMail as soon as your registration fee is received.
If you are a Point system, it will be sent to your BOSS Node.
MAIL THIS FORM WITH PAYMENT TO
╓────────────────────────────╖
║ ║
║ Jim Tanner ║
║ 307 South Marjorie ║
║ Osceola, AR 72370 ║
║ ║
╙────────────────────────────╜
┌──────────────────────────┐
│ Jim Tanner │
│ RiverBend SoftWare │
│ 307 South Marjorie │ <=== Cut Out for Mailing Label
│ Osceola, AR 72370 USA │
└──────────────────────────┘